OpenHelm

Created By
Max Beech2 days ago
Execute one-off or scheduled tasks within a virtual computer that can spin up a real browser, a full coding agent, an email inbox and more. OpenHelm unlocks the ability for your agent to carry out all sorts of tasks, such as: • Deep research on a topic • Emailing + handling responses • Coding work • Updating files What makes OpenHelm the best solution for this: • Underpinned by a powerful AI that monitors work and ensures goals are actually achieved • Browser is SUPER stealthy, meaning it can access more of the web than other bots • Work is managed by a powerful agentic system, facilitating multi-step flows For performing complex, one-off or recurring work, OpenHelm provides a secure, remote environment to make it all possible.
Overview

Execute one-off or scheduled tasks within a virtual computer that can spin up a real browser, a full coding agent, an email inbox and more.

OpenHelm unlocks the ability for your agent to carry out all sorts of tasks, such as:

  • •Deep research on a topic
  • • Emailing + handling responses
  • • Coding work
  • • Updating files

What makes OpenHelm the best solution for this:

  • • Underpinned by a powerful AI that monitors work and ensures goals are actually achieved
  • • Browser is SUPER stealthy, meaning it can access more of the web than other bots
  • • Work is managed by a powerful agentic system, facilitating multi-step flows

For performing complex, one-off or recurring work, OpenHelm provides a secure, remote environment to make it all possible.

Server Config

{
  "mcpServers": {
    "openhelm": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.openhelm.ai/main/mcp"
      ]
    }
  }
}
Project Info
Created At
2 days ago
Updated At
6 hours ago
Author Name
Max Beech
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago